Celestin Apprentice 2

home *** CD-ROM | disk | FTP | other *** search

/ Celestin Apprentice 2 / Apprentice-Release2.iso / Information / Digests / CSMP Digest / volume 3 / csmp-digest-v3-072 < prev next >

Wrap

Text File | 1994-12-08 | 60.1 KB | 324 lines | [TEXT/R*ch]

ustness.... : > : > Which is the best way to go, Apple Events, PPC toolbox, or a combination : > of NBP and ADSP? : Be aware that AppleEvents are based on PPC Toolbox, and PPC Toolbox is : based on ADSP. You probably already knew this, but sometimes it's useful : to hear it out loud. What it means is that no matter which of the three : you pick, your choice will only be as robust as ADSP, but might be less : robust. This might lead you to go with ADSP, if only to reduce the number : of layers involved. However, PPC Toolbox does buy you quicker comm between : processes on the same Mac, and AppleEvents buy you some amount of : simplification, which might end up meaning that the least tested code, : yours, is more robust. Also be aware that ADSP in built on top of DDP. Now I know that ddp is lower level than most want to go, BUT, if you minimum overhead and still maintain compatability, you might consider DDP as an option. One fault of DDP is that it's connection-less, meaning packets can be lost, so if you can't afford that, ADSP is the way to go... Ben Diamand bdiamand@netcom.com +++++++++++++++++++++++++++ >From bdiamand@netcom.com (Ben Diamand) Date: Wed, 16 Nov 1994 03:44:59 GMT Organization: NETCOM On-line Communication Services (408 261-4700 guest) Pete Gontier (pgontier@novell.com) wrote: : In article <gerrard-1211940051400001@131.172.10.162>, : gerrard@luga.latrobe.edu.au (Graeme Gerrard) wrote: : > I need to send messages to a number : > of Macintoshes connected to a host over Localtalk. : > : > ...The main criteria is robustness.... : > : > Which is the best way to go, Apple Events, PPC toolbox, or a combination : > of NBP and ADSP? : Be aware that AppleEvents are based on PPC Toolbox, and PPC Toolbox is : based on ADSP. You probably already knew this, but sometimes it's useful : to hear it out loud. What it means is that no matter which of the three : you pick, your choice will only be as robust as ADSP, but might be less : robust. This might lead you to go with ADSP, if only to reduce the number : of layers involved. However, PPC Toolbox does buy you quicker comm between : processes on the same Mac, and AppleEvents buy you some amount of : simplification, which might end up meaning that the least tested code, : yours, is more robust. Also be aware that ADSP in built on top of DDP. Now I know that ddp is lower level than most want to go, BUT, if you minimum overhead and still maintain compatability, you might consider DDP as an option. One fault of DDP is that it's connection-less, meaning packets can be lost, so if you can't afford that, ADSP is the way to go... Ben Diamand bdiamand@netcom.com +++++++++++++++++++++++++++ >From Chris Russo <chris@sonicsys.com> Date: 17 Nov 1994 01:56:47 GMT Organization: Sonic Systems, Inc. In article <gerrard-1211940051400001@131.172.10.162> Graeme Gerrard, gerrard@luga.latrobe.edu.au writes: >I need to send messages to a number >of Macintoshes connected to a host over Localtalk. > >The remote Macs will be running the *same program* continuously >and different messages need to be sent to them. >The messages are short, a couple of hundred bytes each >and have to be sent every second or so. >The main criteria is robustness. The system has to run, with a minimum of >maintenance, for several months. > >Which is the best way to go, Apple Events, PPC toolbox, or a combination >of NBP and ADSP? > >Advice from anyone with experience in this kind of thing would be >greatly appreciated. Go with NBP and ADSP. Anecdote*: My office-mate wrote Server Sentry, a remote AppleShare admin, using AppleEvents - at first. Unfortunately, he found that AppleEvents sent to a very busy machine can die without notifying the sender of the error. He then took a step back to rely on the PPC toolbox. Then, you still have to mess with program linking's dialogs since the PPC toolbox doesn't allow you to authenticate a user programmatically. He ended up having to patch GetNewDialog() to hide Program Linking's password dialog offscreen while he stuffed the user's name and password iuohio.edu (Bob Williams) Date: 7 Nov 94 19:34:03 -0500 Organization: Enterprise Software In article <ctaylor-0711941646450001@wolfville-ts-15.nstn.ca>, ctaylor@fox.nstn.ns.ca (Christian Taylor) writes: > Could someone please send me some sample source code of a background only > app in Pascal? (THINK Pascal actually). Everytime I try to make a > program background only, the Mac crashes whenever I click in the > Application menu! And yes, I've read the Tech Note from ftp.apple.com on > BOAs. Thanks! > > Christian Me too!!! I have the exact same problem. I posted here once before, but noone answered. I would greatly appreciate it. Thanks!!! Regards, Bob -- +------------------------------------------------------+ | Robert E. Williams, Jr. | | Enterprise Software | | 2006 State Route 380 | | Wilmington, Ohio 45177-9241 | | (513) 382-8232 | | | | E-mail: williar2@miavx1.acs.muohio.edu | +------------------------------------------------------+ | Those who are patient in the trivial things in | | life and control themselves will one day have the | | same mastery in great and important things. | | --Hapkido Master Bong Soo Han | +------------------------------------------------------+ +++++++++++++++++++++++++++ >From chris-b@cs.auckland.ac.nz (Chris Burns) Date: Tue, 08 Nov 1994 22:23:24 +1200 Organization: AucklandUniversity:ComputerScience:HMU In article <1994Nov7.193403.33348@miavx1>, williar2@miavx1.acs.muohio.edu (Bob Williams) wrote: > In article <ctaylor-0711941646450001@wolfville-ts-15.nstn.ca>, ctaylor@fox.nstn.ns.ca (Christian Taylor) writes: > > Could someone please send me some sample source code of a background only > > app in Pascal? (THINK Pascal actually). Everytime I try to make a > > program background only, the Mac crashes whenever I click in the > > Application menu! And yes, I've read the Tech Note from ftp.apple.com on > > BOAs. Thanks! > > Me too!!! I have the exact same problem. I posted here once before, but noone > answered. I would greatly appreciate it. Thanks!!! THINK Pascal automagically places standard toolbox initialization code at the beginning of your app. You need to turn this feature off for BOAs by placing a {$I-} near the top of your main program file. You also need a _MaxApplZone call (expands heap to fullest), an _InitGraf call (sets up your app A5 world) and a few _MoreMasters (to preallocate a few master pointer blocks). Your code goes after this stuff. {-------------------------} {$I-} program blah; begin MaxApplZone; InitGraf(@thePort); MoreMasters; MoreMasters; MoreMasters; end. {-------------------------} Chris B - --------------------------------------------------------------------- NewZealand:AucklandUniversity:ComputerScience:HyperMediaUnit:ChrisBurns Internet: chris-b@cs.auckland.ac.nz Phone: +64 9 373-7599 x6194 Fax: +64 9 373-7453 Async, therefore I am. - --------------------------------------------------------------------- +++++++++++++++++++++++++++ >From asunta@convex.csc.FI (Miika Asunta) Date: 12 Nov 1994 17:08:43 GMT Organization: Sibelius Academy, Helsinki In <1994Nov7.193403.33348@miavx1> williar2@miavx1.acs.muohio.edu (Bob Williams) writes: >In article <ctaylor-0711941646450001@wolfville-ts-15.nstn.ca>, ctaylor@fox.nstn.ns.ca (Christian Taylor) writes: >> Could someone please send me some sample source code of a background only >> app in Pascal? (THINK Pascal actually). Everytime I try to make a >> program background only, the Mac crashes whenever I click in the >> Application menu! And yes, I've read the Tech Note from ftp.apple.com on >> BOAs. Thanks! >> I'm sorry this in in C, but I believe you can read it anyway. The projet type must be 'appe' for background application (NOT 'APPL'). In addition, set 'Only background' size4 17:25:00 GMT Organization: Eugene FreeNet In article <39qqe7$mbp@euas20.eua.ericsson.se> Joakim Grebeno, euajgo@eua.ericsson.se writes: >Would it actually be possible to do a PostEvent() from a task >(interrupt) triggered by the TimeManager, or is it forbidden? PostEvent doesn't move memory, so as long as your time manager routine doesn't move memory (a big no-no), yes, you could post an event. // // Glenn L. Austin // Computer Wizard and Racing Car Driver // Internet: glenn_a@efn.org // +++++++++++++++++++++++++++ >From euajgo@eua.ericsson.se (Joakim Grebeno) Date: 11 Nov 1994 08:14:04 GMT Organization: Ellemtel Telecom Systems Labs, Stockholm, Sweden Glenn L. Austin <glenn_a@efn.org> writes: >In article <39qqe7$mbp@euas20.eua.ericsson.se> Joakim Grebeno, >euajgo@eua.ericsson.se writes: >>Would it actually be possible to do a PostEvent() from a task >>(interrupt) triggered by the TimeManager, or is it forbidden? >PostEvent doesn't move memory, so as long as your time manager routine >doesn't move memory (a big no-no), yes, you could post an event. Thanks! That's one problem out of the way! Furthermore I suppose that I have to setup the my applications A5 world in the task before doing a PostEvent()? If this is the case I'm forced to pass two parameters to the TimeManager task i.e the current A5 *and* the pointer to the function I want to post to the main event loop. Could this really be done? Thanks Joakim -- A: Look! It's a blast-furnace! B: It's a tree branch! A: OK! I can see that now! +++++++++++++++++++++++++++ >From scouten@uiuc.edu (Eric Scouten) Date: Fri, 11 Nov 1994 10:01:38 -0600 Organization: University of Illinois [follow-ups redirected to comp.sys.mac.programmer.help] In article <39v94c$s7h@euas20.eua.ericsson.se>, euajgo@eua.ericsson.se (Joakim Grebeno) wrote: > Thanks! That's one problem out of the way! Furthermore I suppose that I > have to setup the my applications A5 world in the task before doing a > PostEvent()? > If this is the case I'm forced to pass two parameters to the TimeManager > task i.e the current A5 *and* the pointer to the function I want to post to > the main event loop. Could this really be done? Yes, this is very easy to do. Just extend the TMTask record. You can do something like this: struct MyTMTask { TMTask tm; long itsA5; long refCon; // whatever your other parameter was }; -es __________________________________________________________________________ Eric Scouten <scouten@uiuc.edu> * MS Comp Sci '96, Univ of Illinois IMPORTANT NOTICE TO READERS: The entire physical universe, including this message, may one day collapse back into an infinitesimally small space. Should another universe subsequently re-emerge, the existence of this message cannot be guaranteed. -with apologies to Devine & Cohen (Absolute Zero Gravity) +++++++++++++++++++++++++++ >From reed@medicine.wustl.edu (Thomas Reed) Date: Thu, 10 Nov 1994 10:25:25 -0600 Organization: Washington University I dunno if calling PostEvent is legal or not in that case. However, it sounds like for what you need, a safer method might be to have your TM task set a certain global flag, which your main event loop constantly checks for. When you see the flag set, you call the function. I use just this method to draw a picture to the screen every 5 seconds in one of my programs, and it works quite nicely. -Thomas ===================================================== Thomas Reed Washington University reed@telesphere.wustl.edu Medical School reed@medicine.wustl.edu Saint Louis, MO - --------------------------------------------------- Clothes make the man. Naked people have little or no influence on society. -- Mark Twain ===================================================== Opinions posted are not the opinions of Wash. U. +++++++++++++++++++++++++++ >From bdiamand@netcom.com (Ben Diamand) Date: Wed, 16 Nov 1994 04:04:16 GMT Organization: NETCOM On-line Communication Services (408 261-4700 guest) Joakim Grebeno (euajgo@eua.